-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENH: Update reorderItems() to use ORM where possible #336
Conversation
I'm all for simplification, though it seems suspicious that such a big removal will go without an impact in tests. Does it mean something significantly changed somewhere else to still support the reordering? |
Hi @michalkleiner, The module already supported sorting through the ORM, the only thing was that it only used the ORM for The relevant code for sorting through the ORM is still here: |
07fd599
to
ad59dad
Compare
We now have tests covering:
Please let me know if there is anything else I can do to increase confidence in this change. |
I'm slowly reviewing this inbetween other work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, works correctly locally, and the new tests are fantastic. Thanks for doing this.
Can you please rebase and resolve the merge conflict?
446618b
to
c2faf9e
Compare
c2faf9e
to
5041e6c
Compare
Thanks, @GuySartorelli! Rebase complete. I'm not sure why, but running the workflow needs approval, if you could please 😃 . |
Description
Closes #335
Based onto
3
, but please feel free to update that with what you think is appropriate.I'm not 100% familiar with all of the different
Lists
that we have, but I think it would only be theManyManyList
that we still need to process with SQL Queries, as their DB records have no representation in the ORM.Additions
Just added a cheeky little extension point for
onBeforeReorderItems
, because "why not?".